home *** CD-ROM | disk | FTP | other *** search
- Path: bristlecone.together.net!usenet
- From: krw@together.net@krw@together.net
- Newsgroups: comp.dcom.modems
- Subject: Re: Help with IRQ problem
- Date: 26 Jan 1996 03:29:20 GMT
- Organization: TGF Internet Services
- Message-ID: <4e9hqg$rb1@bristlecone.together.net>
- References: <4e79bh$n7e@pulp.ucs.ualberta.ca> <31078218.63005181@news.atl.mindspring.com>
- Reply-To: krw@together.net
- NNTP-Posting-Host: vtr121.ramp.together.net
- X-Newsreader: IBM NewsReader/2 v1.2.5
-
- In <31078218.63005181@news.atl.mindspring.com>, jjerrim@comminfo.com (John Jerrim) writes:
- >bonitlee@gpu1.srv.ualberta.ca (Bonita Lee) wrote:
- >
- >MSD does not do a good job at detecting IRQs used by devices
-
- Sorry that I have to crop quotes so closely, but my News Reader or ISP
- demand ti (they blame each other).
-
- MSD is virtually useless in finding IRQ conflicts. If they were easy enough
- for MSD to find, you'd know about them already. By the way, the IBM OS/2
- RMVIEW is no better, nor is the MWave installation program (configw or
- config). I think the all suffer the same fate. PCs are just not specified
- well enough, and what is specified is ignored. The system manufacturers
- equally to blame ("Who needs to know this theckie stuff").
-
- >MSD "reserved" IRQs are available for use by devices, but MSD
- >generally does not detect when these IRQs are really being used by
- >devices. You should not have a problem getting all of the devices
- >working correctly if you have some degree of flexibility with your IRQ
- >selections.
-
- MSD didn't detect my CDROM, on the second IDE channel, on IRQ 15. My
- system documentation had it on 12 or 14 (depending of whether you
- believed the docs or the jumper settings, both wrong).
-
-
- Keith R. Williams
- krw@together.net
-
-